Skip to content

feat: integrate persistent Hermes memory service & align with upstream/main#155

Open
abdulsamed1 wants to merge 8 commits into
tashfeenahmed:mainfrom
abdulsamed1:main
Open

feat: integrate persistent Hermes memory service & align with upstream/main#155
abdulsamed1 wants to merge 8 commits into
tashfeenahmed:mainfrom
abdulsamed1:main

Conversation

@abdulsamed1

Copy link
Copy Markdown

This PR integrates the Hermes persistent conversation memory system into freellmapi, fully merged with the latest changes from upstream/main (including the dashboard user authentication sessions and the Responses API shim).

Key Features Integrated:

  • Persistent Conversation Memory: Enables long-term chat session history, parent-child lineages (using recursive CTEs), full-text search (FTS5) index syncing, and token/cost metric aggregation.
  • Table Collision Resolution: Renamed the Hermes session database table to chat_sessions to prevent schema conflicts with the upstream dashboard authentication sessions table.
  • Responses API Alignment: Unified route handling so that all Responses API calls properly target the upstream responsesRouter for formatting SSE event streams.
  • Client Stability: Fixed React 19 types within client/src/components/markdown.tsx to ensure clean workspace compilation.

Verification Results

  • All server-side unit, integration, and routing tests build and pass cleanly: 27 test files passed (206 tests).
  • Client and server workspaces built successfully with zero errors.

Copilot AI review requested due to automatic review settings May 31, 2026 16:13

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants